| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CP.2.5.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.2.5 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CP_2_5_Manage_Patient_Originated_Data |
| Title | CP.2.5 Manage Patient-Originated Data (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Capture and explicitly label patient-originated data, link the data source with the data, and support provider authentication for inclusion in patient health record as well as subsequent rendering of the information as part of the health record. |
| Purpose | It is critically important to be able to distinguish clinically authored and authenticated data from patient-originated data that is either provided by the patient for inclusion in the EHR or entered directly into the EHR by the patient from clinically authenticated data. Patients may provide data for entry into the health record or be given a mechanism for entering this data directly. Patient-originated data intended for use by providers will be available for their use. Data about the patient may be appropriately provided by: - the patient; - a surrogate (parent, spouse, guardian) or - an informant (teacher, lawyer, case worker) - devices (e.g., blood pressure/sugar monitors). An electronic health record may provide the ability for direct data entry by any of these. Patient-originated data may also be captured by devices and transmitted for inclusion into the electronic health record. Data entered by any of these must be stored with source information. A provider must authenticate patient-originated data included in the patient's legal health record. A provider must be able to indicate they have verified the accuracy of patient-originated data (when appropriate and when a verification source is available) for inclusion in the patient record. Such verification does not have to occur at each individual data field and can be at a higher level of the data. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Capture and explicitly label patient-originated data, link the data source with the data, and support provider authentication for inclusion in patient health record as well as subsequent rendering of the information as part of the health record.
It is critically important to be able to distinguish clinically authored and authenticated data from patient-originated data that is either provided by the patient for inclusion in the EHR or entered directly into the EHR by the patient from clinically authenticated data. Patients may provide data for entry into the health record or be given a mechanism for entering this data directly. Patient-originated data intended for use by providers will be available for their use.
Data about the patient may be appropriately provided by:
An electronic health record may provide the ability for direct data entry by any of these. Patient-originated data may also be captured by devices and transmitted for inclusion into the electronic health record.
Data entered by any of these must be stored with source information. A provider must authenticate patient-originated data included in the patient's legal health record. A provider must be able to indicate they have verified the accuracy of patient-originated data (when appropriate and when a verification source is available) for inclusion in the patient record. Such verification does not have to occur at each individual data field and can be at a higher level of the data.
| CP.2.5#01 | SHALL |
The system SHALL provide the ability to capture patient- originated data and tag that data as such. |
| CP.2.5#02 | conditional SHALL |
IF the system provides the ability for the patient to capture data directly, THEN the system SHALL tag the data as patient captured. |
| CP.2.5#03 | SHALL |
The system SHALL provide the ability to render patient-originated data. |
| CP.2.5#04 | SHOULD |
The system SHOULD provide the ability for an authorized user to annotate, but not alter, patient-originated data. |
| CP.2.5#05 | SHOULD |
The system SHOULD provide the ability to capture patient-originated annotations on provider-sourced data, and tag the annotations as patient-sourced. |
| CP.2.5#06 | conditional SHALL |
IF the system conforms to function [[CPS.2.1]] (Support for externally-sourced Clinical documents), THEN the system SHALL provide the ability to render externally-sourced clinical documents. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CP.2.5",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Capture and explicitly label patient-originated data, link the data source with the data, and support provider authentication for inclusion in patient health record as well as subsequent rendering of the information as part of the health record.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>It is critically important to be able to distinguish clinically authored and authenticated data from patient-originated data that is either provided by the patient for inclusion in the EHR or entered directly into the EHR by the patient from clinically authenticated data. Patients may provide data for entry into the health record or be given a mechanism for entering this data directly. Patient-originated data intended for use by providers will be available for their use.</p>\n<p>Data about the patient may be appropriately provided by:</p>\n<ul>\n<li>the patient;</li>\n<li>a surrogate (parent, spouse, guardian) or</li>\n<li>an informant (teacher, lawyer, case worker)</li>\n<li>devices (e.g., blood pressure/sugar monitors).</li>\n</ul>\n<p>An electronic health record may provide the ability for direct data entry by any of these. Patient-originated data may also be captured by devices and transmitted for inclusion into the electronic health record.</p>\n<p>Data entered by any of these must be stored with source information. A provider must authenticate patient-originated data included in the patient's legal health record. A provider must be able to indicate they have verified the accuracy of patient-originated data (when appropriate and when a verification source is available) for inclusion in the patient record. Such verification does not have to occur at each individual data field and can be at a higher level of the data.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.2.5#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture patient- originated data and tag that data as such.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.2.5#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system provides the ability for the patient to capture data directly, THEN the system SHALL tag the data as patient captured.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.2.5#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render patient-originated data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.2.5#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for an authorized user to annotate, but not alter, patient-originated data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.2.5#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture patient-originated annotations on provider-sourced data, and tag the annotations as patient-sourced.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.2.5#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system conforms to function [[CPS.2.1]] (Support for externally-sourced Clinical documents), THEN the system SHALL provide the ability to render externally-sourced clinical documents.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.2.5",
"version" : "2.1.0",
"name" : "CP_2_5_Manage_Patient_Originated_Data",
"title" : "CP.2.5 Manage Patient-Originated Data (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Capture and explicitly label patient-originated data, link the data source with the data, and support provider authentication for inclusion in patient health record as well as subsequent rendering of the information as part of the health record.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "It is critically important to be able to distinguish clinically authored and authenticated data from patient-originated data that is either provided by the patient for inclusion in the EHR or entered directly into the EHR by the patient from clinically authenticated data. Patients may provide data for entry into the health record or be given a mechanism for entering this data directly. Patient-originated data intended for use by providers will be available for their use. \n\nData about the patient may be appropriately provided by:\n- the patient;\n- a surrogate (parent, spouse, guardian) or \n- an informant (teacher, lawyer, case worker) \n- devices (e.g., blood pressure/sugar monitors). \n\nAn electronic health record may provide the ability for direct data entry by any of these. Patient-originated data may also be captured by devices and transmitted for inclusion into the electronic health record.\n\nData entered by any of these must be stored with source information. A provider must authenticate patient-originated data included in the patient's legal health record. A provider must be able to indicate they have verified the accuracy of patient-originated data (when appropriate and when a verification source is available) for inclusion in the patient record. Such verification does not have to occur at each individual data field and can be at a higher level of the data.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.2.5-01",
"label" : "CP.2.5#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture patient- originated data and tag that data as such.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.1.3.2#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.2.5-02",
"label" : "CP.2.5#02",
"conformance" : [
"SHALL"
],
"conditionality" : true,
"requirement" : "IF the system provides the ability for the patient to capture data directly, THEN the system SHALL tag the data as patient captured.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.1.3.2#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.2.5-03",
"label" : "CP.2.5#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render patient-originated data.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.1.3.2#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.2.5-04",
"label" : "CP.2.5#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for an authorized user to annotate, but not alter, patient-originated data.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.1.3.2#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.2.5-05",
"label" : "CP.2.5#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture patient-originated annotations on provider-sourced data, and tag the annotations as patient-sourced."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.2.5-06",
"label" : "CP.2.5#06",
"conformance" : [
"SHALL"
],
"conditionality" : true,
"requirement" : "IF the system conforms to function [[CPS.2.1]] (Support for externally-sourced Clinical documents), THEN the system SHALL provide the ability to render externally-sourced clinical documents."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.